home *** CD-ROM | disk | FTP | other *** search
- Path: yama.mcc.ac.uk!rmplc!news
- From: donc@rmplc.co.uk (D. Cameron)
- Newsgroups: comp.sys.amiga.networking
- Subject: Re: ppp registration vs. non-registration
- Date: Tue, 12 Mar 1996 19:19:00 GMT
- Organization: /\/\anic
- Message-ID: <4i773s$d11@spider.rmplc.co.uk>
- References: <722.6640T564T1195@wvlink.mpl.com> <725.6641T576T2624@gate.net> <1025.6643T1416T2349@wvlink.mpl.com>
- Reply-To: donc@rmplc.co.uk
- NNTP-Posting-Host: ayrpop16.rmplc.co.uk
- X-Newsreader: Forte Free Agent 1.0.82
-
- gene_heskett@wvlink.mpl.com (Gene Heskett) wrote:
-
-
- > DB> whats the best method for setting MTU. I asked my provider and
- > DB> they said set it at 297. Should I increase it or decrease it from
- > DB> there.
-
- >297? Find another ISP, that ones terminally stupid! 1500 is the max,
- >and a good starting point. If that ISP can't go 1000+, then its like
- >I said, find another that can.
-
- >Good luck Dave, Gene
-
- Its not quite as simple as this, because if coders of bulk tranfer
- apps dont bother to reset the TCP MSS option then an MTU of 1500
- is pointless because you are not going to recieve TCP packets larger
- than 576 anyway, because this is the default value built into AmiTCP.
- This is slightly off topic but relevant to the whole MTU argument.
-
- Question is, how many apps currently reset it to 1460? Maybe somebody
- would like to to a survey by wedging the setsockopt() call.
-
- --
- donc@rmplc.co.uk
-
-
-